MODSIGN: do not load mok when secure boot disabled
authorLee, Chun-Yi <joeyli.kernel@gmail.com>
Tue, 13 Mar 2018 10:37:59 +0000 (18:37 +0800)
committerSalvatore Bonaccorso <carnil@debian.org>
Sun, 5 Jan 2020 14:40:37 +0000 (14:40 +0000)
commit7c3882359418cf493aa372f2a0220239c6000cb7
treeae15d1cc2e3b56bacfc04371eb1c77ce6691d49b
parent2754a8c106dda3b305f415fa30e113be0fd3c326
MODSIGN: do not load mok when secure boot disabled

The mok can not be trusted when the secure boot is disabled. Which
means that the kernel embedded certificate is the only trusted key.

Due to db/dbx are authenticated variables, they needs manufacturer's
KEK for update. So db/dbx are secure when secureboot disabled.

Cc: David Howells <dhowells@redhat.com>
Cc: Josh Boyer <jwboyer@fedoraproject.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>
Signed-off-by: "Lee, Chun-Yi" <jlee@suse.com>
[Rebased by Luca Boccassi]
[bwh: Forward-ported to 5.0: adjust filename]

Gbp-Pq: Topic features/all/db-mok-keyring
Gbp-Pq: Name 0001-MODSIGN-do-not-load-mok-when-secure-boot-disabled.patch
security/integrity/platform_certs/load_uefi.c